Skip to content

docs: polish release-facing wording#23

Merged
GsCommand merged 1 commit into
mainfrom
codex/polish-wording-in-release-docs
Mar 20, 2026
Merged

docs: polish release-facing wording#23
GsCommand merged 1 commit into
mainfrom
codex/polish-wording-in-release-docs

Conversation

@GsCommand
Copy link
Copy Markdown
Contributor

Motivation

  • Tighten release-facing wording for clarity and tone without changing meaning or release posture.

Description

  • Updated README.md header wording from *Verbs, schemas, and validation for the current v1.1.0 release.* to *Verbs, schemas, and validation for the v1.1.0 release.*.
  • Reworded the IPFS sentence in README.md from You do not need IPFS context to understand or validate the schemas. to IPFS context is not required to understand or validate the schemas..
  • Replaced two generic integrity bullets in SECURITY.md with concrete references: Schema artifacts are covered by checksum-based integrity records (checksums.txt) and Release metadata and publication records are documented in manifest.json and repository history.
  • Files changed: README.md, SECURITY.md; no other content was modified and the docs still state v1.1.0 as current, v1.0.0 as historical/legacy, separate HTTPS hosting and IPFS publication, and no signed release artifacts claim.

Testing

  • Verified target strings existed and were replaced using rg and direct file inspection with nl/sed.
  • Confirmed diffs and repository status using git diff, git diff --stat, git status --short, git show --stat --oneline --no-patch HEAD, and git diff HEAD^ HEAD -- README.md SECURITY.md, and all checks succeeded.

Codex Task

@GsCommand GsCommand merged commit ac88c86 into main Mar 20, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant